SherbyNet - /page/wikibook/entry.mu

Micron Document

<!DOCTYPE html>

<title>Debugging</title>

</head>

<span id="openzim-page-title" class="mw-page-title-main"><span class="mw-page-title-main">Debugging</span></span>

</h1>

</header>

/* start https://en.wikipedia.org/ */

.mw-parser-output .hatnote{font-style:italic}.mw-parser-output div.hatnote{padding-left:1.6em;margin-bottom:0.5em}.mw-parser-output .hatnote i{font-style:normal}.mw-parser-output .hatnote+link+.hatnote{margin-top:-0.5em}@media print{body.ns-0 .mw-parser-output .hatnote{display:none!important}}

/* end https://en.wikipedia.org/ */

</style><div role="note" class="hatnote navigation-not-searchable">"Debug" redirects here. For other uses, see <a href="Debug_(disambiguation)" class="mw-disambig" title="Debug (disambiguation)">Debug (disambiguation)</a>.</div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .hlist dl,.mw-parser-output .hlist ol,.mw-parser-output .hlist ul{margin:0;padding:0}.mw-parser-output .hlist dd,.mw-parser-output .hlist dt,.mw-parser-output .hlist li{margin:0;display:inline}.mw-parser-output .hlist.inline,.mw-parser-output .hlist.inline dl,.mw-parser-output .hlist.inline ol,.mw-parser-output .hlist.inline ul,.mw-parser-output .hlist dl dl,.mw-parser-output .hlist dl ol,.mw-parser-output .hlist dl ul,.mw-parser-output .hlist ol dl,.mw-parser-output .hlist ol ol,.mw-parser-output .hlist ol ul,.mw-parser-output .hlist ul dl,.mw-parser-output .hlist ul ol,.mw-parser-output .hlist ul ul{display:inline}.mw-parser-output .hlist .mw-empty-li{display:none}.mw-parser-output .hlist dt::after{content:": "}.mw-parser-output .hlist dd::after,.mw-parser-output .hlist li::after{content:" · ";font-weight:bold}.mw-parser-output .hlist dd:last-child::after,.mw-parser-output .hlist dt:last-child::after,.mw-parser-output .hlist li:last-child::after{content:none}.mw-parser-output .hlist dd dd:first-child::before,.mw-parser-output .hlist dd dt:first-child::before,.mw-parser-output .hlist dd li:first-child::before,.mw-parser-output .hlist dt dd:first-child::before,.mw-parser-output .hlist dt dt:first-child::before,.mw-parser-output .hlist dt li:first-child::before,.mw-parser-output .hlist li dd:first-child::before,.mw-parser-output .hlist li dt:first-child::before,.mw-parser-output .hlist li li:first-child::before{content:" (";font-weight:normal}.mw-parser-output .hlist dd dd:last-child::after,.mw-parser-output .hlist dd dt:last-child::after,.mw-parser-output .hlist dd li:last-child::after,.mw-parser-output .hlist dt dd:last-child::after,.mw-parser-output .hlist dt dt:last-child::after,.mw-parser-output .hlist dt li:last-child::after,.mw-parser-output .hlist li dd:last-child::after,.mw-parser-output .hlist li dt:last-child::after,.mw-parser-output .hlist li li:last-child::after{content:")";font-weight:normal}.mw-parser-output .hlist ol{counter-reset:listitem}.mw-parser-output .hlist ol>li{counter-increment:listitem}.mw-parser-output .hlist ol>li::before{content:" "counter(listitem)"\a0 "}.mw-parser-output .hlist dd ol>li:first-child::before,.mw-parser-output .hlist dt ol>li:first-child::before,.mw-parser-output .hlist li ol>li:first-child::before{content:" ("counter(listitem)"\a0 "}

/* end https://en.wikipedia.org/ */

</style><style data-mw-deduplicate="TemplateStyles:r1246091330">

/* start https://en.wikipedia.org/ */

.mw-parser-output .sidebar{width:22em;float:right;clear:right;margin:0.5em 0 1em 1em;background:var(--background-color-neutral-subtle,#f8f9fa);border:1px solid var(--border-color-base,#a2a9b1);padding:0.2em;text-align:center;line-height:1.4em;font-size:88%;border-collapse:collapse;display:table}body.skin-minerva .mw-parser-output .sidebar{display:table!important;float:right!important;margin:0.5em 0 1em 1em!important}.mw-parser-output .sidebar-subgroup{width:100%;margin:0;border-spacing:0}.mw-parser-output .sidebar-left{float:left;clear:left;margin:0.5em 1em 1em 0}.mw-parser-output .sidebar-none{float:none;clear:both;margin:0.5em 1em 1em 0}.mw-parser-output .sidebar-outer-title{padding:0 0.4em 0.2em;font-size:125%;line-height:1.2em;font-weight:bold}.mw-parser-output .sidebar-top-image{padding:0.4em}.mw-parser-output .sidebar-top-caption,.mw-parser-output .sidebar-pretitle-with-top-image,.mw-parser-output .sidebar-caption{padding:0.2em 0.4em 0;line-height:1.2em}.mw-parser-output .sidebar-pretitle{padding:0.4em 0.4em 0;line-height:1.2em}.mw-parser-output .sidebar-title,.mw-parser-output .sidebar-title-with-pretitle{padding:0.2em 0.8em;font-size:145%;line-height:1.2em}.mw-parser-output .sidebar-title-with-pretitle{padding:0.1em 0.4em}.mw-parser-output .sidebar-image{padding:0.2em 0.4em 0.4em}.mw-parser-output .sidebar-heading{padding:0.1em 0.4em}.mw-parser-output .sidebar-content{padding:0 0.5em 0.4em}.mw-parser-output .sidebar-content-with-subgroup{padding:0.1em 0.4em 0.2em}.mw-parser-output .sidebar-above,.mw-parser-output .sidebar-below{padding:0.3em 0.8em;font-weight:bold}.mw-parser-output .sidebar-collapse .sidebar-above,.mw-parser-output .sidebar-collapse .sidebar-below{border-top:1px solid #aaa;border-bottom:1px solid #aaa}.mw-parser-output .sidebar-navbar{text-align:right;font-size:115%;padding:0 0.4em 0.4em}.mw-parser-output .sidebar-list-title{padding:0 0.4em;text-align:left;font-weight:bold;line-height:1.6em;font-size:105%}.mw-parser-output .sidebar-list-title-c{padding:0 0.4em;text-align:center;margin:0 3.3em}@media(max-width:640px){body.mediawiki .mw-parser-output .sidebar{width:100%!important;clear:both;float:none!important;margin-left:0!important;margin-right:0!important}}body.skin--responsive .mw-parser-output .sidebar a>img{max-width:none!important}@media screen{html.skin-theme-clientpref-night .mw-parser-output .sidebar:not(.notheme) .sidebar-list-title,html.skin-theme-clientpref-night .mw-parser-output .sidebar:not(.notheme) .sidebar-title-with-pretitle{background:transparent!important}html.skin-theme-clientpref-night .mw-parser-output .sidebar:not(.notheme) .sidebar-title-with-pretitle a{color:var(--color-progressive)!important}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .sidebar:not(.notheme) .sidebar-list-title,html.skin-theme-clientpref-os .mw-parser-output .sidebar:not(.notheme) .sidebar-title-with-pretitle{background:transparent!important}html.skin-theme-clientpref-os .mw-parser-output .sidebar:not(.notheme) .sidebar-title-with-pretitle a{color:var(--color-progressive)!important}}@media print{body.ns-0 .mw-parser-output .sidebar{display:none!important}}

/* end https://en.wikipedia.org/ */

</style><table class="sidebar sidebar-collapse nomobile"><tbody><tr><td class="sidebar-pretitle">Part of a series on</td></tr><tr><th class="sidebar-title-with-pretitle"><a href="Software_development" title="Software development">Software development</a></th></tr><tr><td class="sidebar-content">

<div class="sidebar-list mw-collapsible"><div class="sidebar-list-title" style="color: var(--color-base)">Core activities</div><div class="sidebar-list-content mw-collapsible-content hlist">

<ul><li><a href="Data_modeling" title="Data modeling">Data modeling</a></li>

<li><a href="Software_development_process" title="Software development process">Processes</a></li>

<li><a href="Requirements_analysis" title="Requirements analysis">Requirements</a></li>

<li><a href="Software_design" title="Software design">Design</a></li>

<li><a href="Software_construction" title="Software construction">Construction</a></li>

<li><a href="Software_engineering" title="Software engineering">Engineering</a></li>

<li><a href="Software_testing" title="Software testing">Testing</a></li>

<li><a href="Software_deployment" title="Software deployment">Deployment</a></li>

<li><a href="Software_maintenance" title="Software maintenance">Maintenance</a></li></ul></div></div></td>

</tr><tr><td class="sidebar-content">

<div class="sidebar-list mw-collapsible mw-collapsed"><div class="sidebar-list-title" style="color: var(--color-base)">Paradigms and models</div><div class="sidebar-list-content mw-collapsible-content hlist">

<ul><li><a href="Agile_software_development" title="Agile software development">Agile</a></li>

<li><a href="Cleanroom_software_engineering" title="Cleanroom software engineering">Cleanroom</a></li>

<li><a href="Incremental_build_model" title="Incremental build model">Incremental</a></li>

<li><a href="Software_prototyping" title="Software prototyping">Prototyping</a></li>

<li><a href="Spiral_model" title="Spiral model">Spiral</a></li>

<li><a href="V-model_(software_development)" title="V-model (software development)">V model</a></li>

<li><a href="Waterfall_model" title="Waterfall model">Waterfall</a></li></ul></div></div></td>

</tr><tr><td class="sidebar-content">

<div class="sidebar-list mw-collapsible mw-collapsed"><div class="sidebar-list-title" style="color: var(--color-base)"><a href="Software_development_methodology" class="mw-redirect" title="Software development methodology">Methodologies</a> and frameworks</div><div class="sidebar-list-content mw-collapsible-content hlist">

<li><a href="DevOps" title="DevOps">DevOps</a></li>

<li><a href="Kanban_(development)" title="Kanban (development)">Kanban</a></li>

<li><a href="Scrum_(software_development)" title="Scrum (software development)">Scrum</a></li>

<li><a href="SEMAT" title="SEMAT">SEMAT</a></li>

</tr><tr><td class="sidebar-content">

<div class="sidebar-list mw-collapsible mw-collapsed"><div class="sidebar-list-title" style="color: var(--color-base)">Supporting disciplines</div><div class="sidebar-list-content mw-collapsible-content hlist">

<ul><li><a href="Software_configuration_management" title="Software configuration management">Configuration management</a></li>

<li><a href="Deployment_management#Computer_science" title="Deployment management">Deployment management</a></li>

<li><a href="Software_documentation" title="Software documentation">Documentation</a></li>

<li><a href="Software_project_management" title="Software project management">Project management</a></li>

<li><a href="Software_quality_assurance" title="Software quality assurance">Quality assurance</a></li>

<li><a href="User_experience" title="User experience">User experience</a></li></ul></div></div></td>

</tr><tr><td class="sidebar-content">

<div class="sidebar-list mw-collapsible mw-collapsed"><div class="sidebar-list-title" style="color: var(--color-base)">Practices</div><div class="sidebar-list-content mw-collapsible-content hlist">

<li><a href="Stand-up_meeting" title="Stand-up meeting">Stand-up</a></li>

</tr><tr><td class="sidebar-content">

<div class="sidebar-list mw-collapsible mw-collapsed"><div class="sidebar-list-title" style="color: var(--color-base)"><a href="Programming_tool" title="Programming tool">Tools</a></div><div class="sidebar-list-content mw-collapsible-content hlist">

<ul><li><a href="Build_automation" title="Build automation">Build automation</a></li>

<li><a href="Compiler" title="Compiler">Compiler</a></li>

<li><a href="Debugger" title="Debugger">Debugger</a></li>

<li><a href="Graphical_user_interface_builder" title="Graphical user interface builder">GUI builder</a></li>

<li><a href="Infrastructure_as_code" title="Infrastructure as code">Infrastructure as code</a></li>

<li><a href="Profiling_(computer_programming)" title="Profiling (computer programming)">Profiler</a></li>

<li><a href="Application-release_automation" title="Application-release automation">Release automation</a></li>

<li><a href="UML_tool" title="UML tool">UML Modeling</a></li></ul></div></div></td>

</tr><tr><td class="sidebar-content">

<div class="sidebar-list mw-collapsible mw-collapsed"><div class="sidebar-list-title" style="color: var(--color-base)">Standards and bodies of knowledge</div><div class="sidebar-list-content mw-collapsible-content hlist">

<li><a href="IEEE_Standards_Association" title="IEEE Standards Association">IEEE standards</a></li>

<li><a href="ISO/IEC_JTC_1/SC_7" title="ISO/IEC JTC 1/SC 7">ISO/IEC standards</a></li>

<li><a href="Project_Management_Body_of_Knowledge" title="Project Management Body of Knowledge">PMBOK</a></li>

<li><a href="Software_Engineering_Body_of_Knowledge" title="Software Engineering Body of Knowledge">SWEBOK</a></li></ul></div></div></td>

</tr><tr><td class="sidebar-content">

<div class="sidebar-list mw-collapsible mw-collapsed"><div class="sidebar-list-title" style="color: var(--color-base)">Glossaries</div><div class="sidebar-list-content mw-collapsible-content hlist">

<ul><li><a href="Glossary_of_artificial_intelligence" title="Glossary of artificial intelligence">Artificial intelligence</a></li>

<li><a href="Glossary_of_computer_science" title="Glossary of computer science">Computer science</a></li>

<li><a href="Glossary_of_electrical_and_electronics_engineering" title="Glossary of electrical and electronics engineering">Electrical and electronics engineering</a></li></ul></div></div></td>

</tr><tr><td class="sidebar-content">

<div class="sidebar-list mw-collapsible mw-collapsed"><div class="sidebar-list-title" style="color: var(--color-base)">Outlines</div><div class="sidebar-list-content mw-collapsible-content hlist">

<ul><li><a href="Outline_of_software_development" title="Outline of software development">Outline of software development</a></li></ul></div></div></td>

</tr><tr><td class="sidebar-navbar"><style data-mw-deduplicate="TemplateStyles:r1239400231">

/* start https://en.wikipedia.org/ */

.mw-parser-output .navbar{display:inline;font-size:88%;font-weight:normal}.mw-parser-output .navbar-collapse{float:left;text-align:left}.mw-parser-output .navbar-boxtext{word-spacing:0}.mw-parser-output .navbar ul{display:inline-block;white-space:nowrap;line-height:inherit}.mw-parser-output .navbar-brackets::before{margin-right:-0.125em;content:"[ "}.mw-parser-output .navbar-brackets::after{margin-left:-0.125em;content:" ]"}.mw-parser-output .navbar li{word-spacing:-0.125em}.mw-parser-output .navbar a>span,.mw-parser-output .navbar a>abbr{text-decoration:inherit}.mw-parser-output .navbar-mini abbr{font-variant:small-caps;border-bottom:none;text-decoration:none;cursor:inherit}.mw-parser-output .navbar-ct-full{font-size:114%;margin:0 7em}.mw-parser-output .navbar-ct-mini{font-size:114%;margin:0 4em}html.skin-theme-clientpref-night .mw-parser-output .navbar li a abbr{color:var(--color-base)!important}@media(prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .navbar li a abbr{color:var(--color-base)!important}}@media print{.mw-parser-output .navbar{display:none!important}}

/* end https://en.wikipedia.org/ */

</style></td></tr></tbody></table>

<p>In <a href="Engineering" title="Engineering">engineering</a>, <b>debugging</b> is the process of finding the <a href="Root_cause_analysis" title="Root cause analysis">root cause</a>, <a href="Workaround" title="Workaround">workarounds</a>, and possible fixes for <a href="Bug_(engineering)" title="Bug (engineering)">bugs</a>.

</p><p>For <a href="Software" title="Software">software</a>, debugging tactics can involve <a href="Interactive" class="mw-redirect" title="Interactive">interactive</a> debugging, <a href="Control_flow" title="Control flow">control flow</a> analysis, <a href="Logfile" class="mw-redirect" title="Logfile">log file analysis</a>, monitoring at the <a href="Application_monitoring" class="mw-redirect" title="Application monitoring">application</a> or <a href="System_monitoring" class="mw-redirect" title="System monitoring">system</a> level, <a href="Memory_dump" class="mw-redirect" title="Memory dump">memory dumps</a>, and <a href="Profiling_(computer_programming)" title="Profiling (computer programming)">profiling</a>. Many <a href="Programming_language" title="Programming language">programming languages</a> and <a href="Programming_tool" title="Programming tool">software development tools</a> also offer programs to aid in debugging, known as <a href="Debugger" title="Debugger">debuggers</a>.

</p>

<div class="mw-heading mw-heading2"><h2 id="Etymology">Etymology</h2></div>

<div role="note" class="hatnote navigation-not-searchable">See also: <a href="Bug_(engineering)#History" title="Bug (engineering)">Bug (engineering) § History</a></div>

<p>The term <i>bug</i>, in the sense of defect, dates back at least to 1878 when <a href="Thomas_Edison" title="Thomas Edison">Thomas Edison</a> wrote "little faults and difficulties" in his inventions as "Bugs".

</p><p>A popular story from the 1940s is from <a href="Admiral_Grace_Hopper" class="mw-redirect" title="Admiral Grace Hopper">Admiral Grace Hopper</a>.<sup id="cite_ref-1" class="reference"><a href="#cite_note-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup> While she was working on a <a href="Harvard_Mark_II" title="Harvard Mark II">Mark II</a> computer at Harvard University, her associates discovered a <a href="Moth" title="Moth">moth</a> stuck in a relay that impeded operation and wrote in a log book "First actual case of a bug being found". Although probably a <a href="Word_play" title="Word play">joke</a>, conflating the two meanings of bug (biological and defect), the story indicates that the term was used in the computer field at that time.

</p><p>Similarly, the term <i>debugging</i> was used in aeronautics before entering the world of <a href="Computer" title="Computer">computers</a>. A letter from <a href="J._Robert_Oppenheimer" title="J. Robert Oppenheimer">J. Robert Oppenheimer</a>, director of the <a href="WWII" class="mw-redirect" title="WWII">WWII</a> atomic bomb <a href="Manhattan_Project" title="Manhattan Project">Manhattan Project</a> at Los Alamos, used the term in a letter to Dr. <a href="Ernest_Lawrence" title="Ernest Lawrence">Ernest Lawrence</a> at UC Berkeley, dated October 27, 1944,<sup id="cite_ref-2" class="reference"><a href="#cite_note-2"><span class="cite-bracket">[</span>2<span class="cite-bracket">]</span></a></sup> regarding the recruitment of additional technical staff.

The <a href="Oxford_English_Dictionary" title="Oxford English Dictionary">Oxford English Dictionary</a> entry for <i>debug</i> uses the term <i>debugging</i> in reference to airplane engine testing in a 1945 article in the Journal of the Royal Aeronautical Society.

An article in "Airforce" (June 1945 p. 50) refers to <i>debugging</i> aircraft cameras.

</p><p>The seminal article by Gill<sup id="cite_ref-3" class="reference"><a href="#cite_note-3"><span class="cite-bracket">[</span>3<span class="cite-bracket">]</span></a></sup> in 1951 is the earliest in-depth discussion of programming errors, but it does not use the term <i>bug</i> or <i>debugging</i>.

</p><p>In the <a href="Association_for_Computing_Machinery" title="Association for Computing Machinery">ACM</a>'s digital library, the term <i>debugging</i> is first used in three papers from the 1952 ACM National Meetings.<sup id="cite_ref-4" class="reference"><a href="#cite_note-4"><span class="cite-bracket">[</span>4<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-5" class="reference"><a href="#cite_note-5"><span class="cite-bracket">[</span>5<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-6" class="reference"><a href="#cite_note-6"><span class="cite-bracket">[</span>6<span class="cite-bracket">]</span></a></sup> Two of the three use the term in quotation marks.

</p><p>By 1963, <i>debugging</i> was a common enough term to be mentioned in passing without explanation on page 1 of the <a href="Compatible_Time-Sharing_System" title="Compatible Time-Sharing System">CTSS</a> manual.<sup id="cite_ref-7" class="reference"><a href="#cite_note-7"><span class="cite-bracket">[</span>7<span class="cite-bracket">]</span></a></sup>

</p>

<div class="mw-heading mw-heading2"><h2 id="Scope">Scope</h2></div>

<p>As software and electronic systems have become generally more complex, the various common debugging techniques have expanded with more methods to detect anomalies, assess impact, and schedule <a href="Software_patch" class="mw-redirect" title="Software patch">software patches</a> or full updates to a system. The words "anomaly" and "discrepancy" can be used, as being <a href="Euphemism" title="Euphemism">more neutral terms</a>, to avoid the words "error" and "defect" or "bug" where there might be an implication that all so-called <i>errors</i>, <i>defects</i> or <i>bugs</i> must be fixed (at all costs). Instead, an <a href="Impact_assessment" title="Impact assessment">impact assessment</a> can be made to determine if changes to remove an <i>anomaly</i> (or <i>discrepancy</i>) would be cost-effective for the system, or perhaps a scheduled new release might render the change(s) unnecessary. Not all issues are <a href="Safety-critical_system" title="Safety-critical system">safety-critical</a> or <a href="Mission-critical" class="mw-redirect" title="Mission-critical">mission-critical</a> in a system. Also, it is important to avoid the situation where a change might be more upsetting to users, long-term, than living with the known problem(s) (where the "cure would be worse than the disease"). Basing decisions of the acceptability of some anomalies can avoid a culture of a "zero-defects" mandate, where people might be tempted to deny the existence of problems so that the result would appear as zero <i>defects</i>. Considering the collateral issues, such as the cost-versus-benefit impact assessment, then broader debugging techniques will expand to determine the frequency of anomalies (how often the same "bugs" occur) to help assess their impact to the overall system.

</p>

<div class="mw-heading mw-heading2"><h2 id="Tools">Tools</h2></div>

<div role="note" class="hatnote navigation-not-searchable">Main article: <a href="Debugger" title="Debugger">Debugger</a></div>

<p>Debugging ranges in complexity from fixing simple errors to performing lengthy and tiresome tasks of data collection, analysis, and scheduling updates. The debugging skill of the programmer can be a major factor in the ability to debug a problem, but the difficulty of software debugging varies greatly with the complexity of the system, and also depends, to some extent, on the <a href="Programming_language" title="Programming language">programming language</a>(s) used and the available tools, such as <i><a href="Debugger" title="Debugger">debuggers</a></i>. Debuggers are software tools which enable the <a href="Programmer" title="Programmer">programmer</a> to monitor the <a href="Execution_(computing)" title="Execution (computing)">execution</a> of a program, stop it, restart it, set <a href="Breakpoint" title="Breakpoint">breakpoints</a>, and change values in memory. The term <i>debugger</i> can also refer to the person who is doing the debugging.

</p><p>Generally, <a href="High-level_programming_language" title="High-level programming language">high-level programming languages</a>, such as <a href="Java_(programming_language)" title="Java (programming language)">Java</a>, make debugging easier, because they have features such as <a href="Exception_handling" title="Exception handling">exception handling</a> and <a href="Type_checking" class="mw-redirect" title="Type checking">type checking</a> that make real sources of erratic behaviour easier to spot. In programming languages such as <a href="C_(programming_language)" title="C (programming language)">C</a> or <a href="Assembly_language" title="Assembly language">assembly</a>, bugs may cause silent problems such as <a href="Memory_corruption" title="Memory corruption">memory corruption</a>, and it is often difficult to see where the initial problem happened. In those cases, <a href="Memory_debugging" class="mw-redirect" title="Memory debugging">memory debugger</a> tools may be needed.

</p><p>In certain situations, general purpose software tools that are language specific in nature can be very useful. These take the form of <i><a href="List_of_tools_for_static_code_analysis" title="List of tools for static code analysis">static code analysis tools</a></i>. These tools look for a very specific set of known problems, some common and some rare, within the source code, concentrating more on the semantics (e.g. data flow) rather than the syntax, as compilers and interpreters do.

</p><p>Both commercial and free tools exist for various languages; some claim to be able to detect hundreds of different problems. These tools can be extremely useful when checking very large source trees, where it is impractical to do code walk-throughs. A typical example of a problem detected would be a variable dereference that occurs <i>before</i> the variable is assigned a value. As another example, some such tools perform strong type checking when the language does not require it. Thus, they are better at locating likely errors in code that is syntactically correct. But these tools have a reputation of false positives, where correct code is flagged as dubious. The old Unix <i><a href="Lint_(software)" title="Lint (software)">lint</a></i> program is an early example.

</p><p>For debugging electronic hardware (e.g., <a href="Computer_hardware" title="Computer hardware">computer hardware</a>) as well as low-level software (e.g., <a href="BIOS" title="BIOS">BIOSes</a>, <a href="Device_driver" title="Device driver">device drivers</a>) and <a href="Firmware" title="Firmware">firmware</a>, instruments such as <a href="Oscilloscope" title="Oscilloscope">oscilloscopes</a>, <a href="Logic_analyzer" title="Logic analyzer">logic analyzers</a>, or <a href="In-circuit_emulator" class="mw-redirect" title="In-circuit emulator">in-circuit emulators</a> (ICEs) are often used, alone or in combination. An ICE may perform many of the typical software debugger's tasks on low-level <a href="Software" title="Software">software</a> and <a href="Firmware" title="Firmware">firmware</a>.

</p>

<div class="mw-heading mw-heading2"><h2 id="Debugging_process">Debugging process</h2></div>

<p>The debugging process normally begins with identifying the steps to reproduce the problem. This can be a non-trivial task, particularly with parallel processes and some <a href="Heisenbug" title="Heisenbug">Heisenbugs</a> for example. The specific <a href="User_environment" class="mw-redirect" title="User environment">user environment</a> and usage history can also make it difficult to reproduce the problem.

</p><p>After the bug is reproduced, the input of the program may need to be simplified to make it easier to debug. For example, a bug in a compiler can make it <a href="Crash_(computing)" title="Crash (computing)">crash</a> when parsing a large source file. However, after simplification of the test case, only few lines from the original source file can be sufficient to reproduce the same crash. Simplification may be done manually using a <a href="Divide-and-conquer_algorithm" title="Divide-and-conquer algorithm">divide-and-conquer</a> approach, in which the programmer attempts to remove some parts of original test case then checks if the problem still occurs. When debugging in a <a href="Graphical_user_interface" title="Graphical user interface">GUI</a>, the programmer can try skipping some user interaction from the original problem description to check if the remaining actions are sufficient for causing the bug to occur.

</p><p>After the test case is sufficiently simplified, a programmer can use a debugger tool to examine program states (values of variables, plus the <a href="Call_stack" title="Call stack">call stack</a>) and track down the origin of the problem(s). Alternatively, <a href="Tracing_(software)" title="Tracing (software)">tracing</a> can be used. In simple cases, tracing is just a few print statements which output the values of variables at particular points during the execution of the program.

</p>

<div class="mw-heading mw-heading2"><h2 id="Techniques">Techniques</h2></div>

<ul><li><i>Interactive debugging</i> uses debugger tools which allow a program's execution to be processed one step at a time and to be paused to inspect or alter its state. Subroutines or function calls may typically be executed at full speed and paused again upon return to their caller, or themselves single stepped, or any mixture of these options. Setpoints may be installed which permit full speed execution of code that is not suspected to be faulty, and then stop at a point that is. Putting a setpoint immediately after the end of a program loop is a convenient way to evaluate repeating code. Watchpoints are commonly available, where execution can proceed until a particular variable changes, and catchpoints which cause the debugger to stop for certain kinds of program events, such as exceptions or the loading of a shared library.</li>

/* start https://en.wikipedia.org/ */

.mw-parser-output .vanchor>:target~.vanchor-text{background-color:#b1d2ff}@media screen{html.skin-theme-clientpref-night .mw-parser-output .vanchor>:target~.vanchor-text{background-color:#0f4dc9}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .vanchor>:target~.vanchor-text{background-color:#0f4dc9}}

/* end https://en.wikipedia.org/ */

</style><span class="vanchor"><span class="vanchor-text">Print debugging</span></span></i> or <i><a href="Tracing_(software)" title="Tracing (software)">tracing</a></i> is the act of watching (live or recorded) trace statements, or print statements, that indicate the flow of execution of a process and the data progression. Tracing can be done with specialized tools (like with GDB's trace) or by insertion of trace statements into the source code. The latter is sometimes called <i><span class="vanchor"><span class="vanchor-text">printf debugging</span></span></i>, due to the use of the <a href="Printf" title="Printf">printf</a> function in C. This kind of debugging was turned on by the command TRON in the original versions of the novice-oriented <a href="BASIC" title="BASIC">BASIC</a> programming language. TRON stood for, "Trace On." TRON caused the line numbers of each BASIC command line to print as the program ran.</li>

<li><i>Activity tracing</i> is like tracing (above), but rather than following program execution one instruction or function at a time, follows program activity based on the overall amount of time spent by the processor/CPU executing particular segments of code. This is typically presented as a fraction of the program's execution time spent processing instructions within defined memory addresses (machine code programs) or certain program modules (high level language or compiled programs). If the program being debugged is shown to be spending an inordinate fraction of its execution time within traced areas, this could indicate misallocation of processor time caused by faulty program logic, or at least inefficient allocation of processor time that could benefit from optimization efforts.</li>

<li><i><span class="vanchor"><span class="vanchor-text">Remote debugging</span></span></i> is the process of debugging a program running on a system different from the debugger. To start remote debugging, a debugger connects to a remote system over a communications link such as a local area network. The debugger can then control the execution of the program on the remote system and retrieve information about its state.</li>

<li><i>Post-mortem debugging</i> is debugging of the program after it has already <a href="Crash_(computing)" title="Crash (computing)">crashed</a>. Related techniques often include various tracing techniques like examining log files, outputting a <a href="Call_stack" title="Call stack">call stack</a> on the crash,<sup id="cite_ref-8" class="reference"><a href="#cite_note-8"><span class="cite-bracket">[</span>8<span class="cite-bracket">]</span></a></sup> and analysis of <a href="Memory_dump" class="mw-redirect" title="Memory dump">memory dump</a> (or <a href="Core_dump" title="Core dump">core dump</a>) of the crashed process. The dump of the process could be obtained automatically by the system (for example, when the process has terminated due to an unhandled exception), or by a programmer-inserted instruction, or manually by the interactive user.</li>

<li><i>"Wolf fence" algorithm:</i> Edward Gauss described this simple but very useful and now famous algorithm in a 1982 article for <a href="Communications_of_the_ACM" title="Communications of the ACM">Communications of the ACM</a> as follows: "There's one wolf in Alaska; how do you find it? First build a fence down the middle of the state, wait for the wolf to howl, determine which side of the fence it is on. Repeat process on that side only, until you get to the point where you can see the wolf."<sup id="cite_ref-9" class="reference"><a href="#cite_note-9"><span class="cite-bracket">[</span>9<span class="cite-bracket">]</span></a></sup> This is implemented e.g. in the <a href="Git_(software)" class="mw-redirect" title="Git (software)">Git</a> <a href="Version_control_system" class="mw-redirect" title="Version control system">version control system</a> as the command <i>git bisect</i>, which uses the above algorithm to determine which <a href="Commit_(data_management)" title="Commit (data management)">commit</a> introduced a particular bug.</li>

<li><i><a href="Record_and_replay_debugging" title="Record and replay debugging">Record and replay debugging</a></i> is the technique of creating a program execution recording (e.g. using Mozilla's free <a href="Rr_(debugging)" title="Rr (debugging)">rr</a> debugging tool; enabling reversible debugging/execution), which can be replayed and interactively debugged. Useful for remote debugging and debugging intermittent, non-deterministic, and other hard-to-reproduce defects.</li>

<li><i><a href="Time_travel_debugging" title="Time travel debugging">Time travel debugging</a></i> is the process of stepping back in time through source code (e.g. using <a href="Undo_(company)" title="Undo (company)">Undo LiveRecorder</a>) to understand what is happening during execution of a computer program; to allow users to interact with the program; to change the history if desired and to watch how the program responds.</li>

<li><i><a href="Delta_debugging" title="Delta debugging">Delta debugging</a></i> – a technique of automating test case simplification.<sup id="cite_ref-10" class="reference"><a href="#cite_note-10"><span class="cite-bracket">[</span>10<span class="cite-bracket">]</span></a></sup><sup class="reference nowrap"><span title="Page / location: p.123">: p.123 </span></sup></li>

<li><i>Saff Squeeze</i> – a technique of isolating failure within the test using progressive inlining of parts of the failing test.<sup id="cite_ref-11" class="reference"><a href="#cite_note-11"><span class="cite-bracket">[</span>11<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-12" class="reference"><a href="#cite_note-12"><span class="cite-bracket">[</span>12<span class="cite-bracket">]</span></a></sup></li>

<li><i>Causality tracking</i>: There are techniques to track the cause effect chains in the computation.<sup id="cite_ref-13" class="reference"><a href="#cite_note-13"><span class="cite-bracket">[</span>13<span class="cite-bracket">]</span></a></sup> Those techniques can be tailored for specific bugs, such as null pointer dereferences.<sup id="cite_ref-BondNethercote2007_14-0" class="reference"><a href="#cite_note-BondNethercote2007-14"><span class="cite-bracket">[</span>14<span class="cite-bracket">]</span></a></sup></li></ul>

<div class="mw-heading mw-heading3"><h3 id="Automatic_bug_fixing">Automatic bug fixing</h3></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .excerpt-hat .mw-editsection-like{font-style:normal}

/* end https://en.wikipedia.org/ */

</style><div role="note" class="hatnote navigation-not-searchable dablink excerpt-hat selfref">This section is an excerpt from <a href="Automatic_bug_fixing" title="Automatic bug fixing">Automatic bug fixing</a>.<span class="mw-editsection-like "><span class="mw-editsection-bracket">[</span><a class="external text external" href="https://en.wikipedia.org/w/index.php?title=Automatic_bug_fixing&action=edit">edit</a><span class="mw-editsection-bracket">]</span></span></div><div class="excerpt">

<a href="Automatic_bug_fixing" title="Automatic bug fixing">Automatic bug-fixing</a> is the automatic <a href="Patch_(computing)" title="Patch (computing)">repair</a> of <a href="Software_bug" title="Software bug">software bugs</a> without the intervention of a human programmer.<sup id="cite_ref-15" class="reference"><a href="#cite_note-15"><span class="cite-bracket">[</span>15<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-16" class="reference"><a href="#cite_note-16"><span class="cite-bracket">[</span>16<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-Automatic_bug_fixing_Gazzola2019_17-0" class="reference"><a href="#cite_note-Automatic_bug_fixing_Gazzola2019-17"><span class="cite-bracket">[</span>17<span class="cite-bracket">]</span></a></sup> It is also commonly referred to as <i>automatic patch generation</i>, <i>automatic bug repair</i>, or <i>automatic program repair</i>.<sup id="cite_ref-Automatic_bug_fixing_Gazzola2019_17-1" class="reference"><a href="#cite_note-Automatic_bug_fixing_Gazzola2019-17"><span class="cite-bracket">[</span>17<span class="cite-bracket">]</span></a></sup> The typical goal of such techniques is to automatically generate correct <a href="Patch_(computing)" title="Patch (computing)">patches</a> to eliminate bugs in <a href="Software_program" class="mw-redirect" title="Software program">software programs</a> without causing <a href="Software_regression" title="Software regression">software regression</a>.<sup id="cite_ref-18" class="reference"><a href="#cite_note-18"><span class="cite-bracket">[</span>18<span class="cite-bracket">]</span></a></sup></div></div>

<div class="mw-heading mw-heading2"><h2 id="Debugging_for_embedded_systems">Debugging for embedded systems</h2></div>

<p>In contrast to the general purpose computer software design environment, a primary characteristic of embedded environments is the sheer number of different platforms available to the developers (CPU architectures, vendors, operating systems, and their variants). Embedded systems are, by definition, not general-purpose designs: they are typically developed for a single task (or small range of tasks), and the platform is chosen specifically to optimize that application. Not only does this fact make life tough for embedded system developers, it also makes debugging and testing of these systems harder as well, since different debugging tools are needed for different platforms.

</p><p>Despite the challenge of heterogeneity mentioned above, some debuggers have been developed commercially as well as research prototypes. Examples of commercial solutions come from <a href="Green_Hills_Software" title="Green Hills Software">Green Hills Software</a>,<sup id="cite_ref-19" class="reference"><a href="#cite_note-19"><span class="cite-bracket">[</span>19<span class="cite-bracket">]</span></a></sup> <a href="Lauterbach_GmbH" class="mw-redirect" title="Lauterbach GmbH">Lauterbach GmbH</a><sup id="cite_ref-20" class="reference"><a href="#cite_note-20"><span class="cite-bracket">[</span>20<span class="cite-bracket">]</span></a></sup> and Microchip's MPLAB-ICD (for in-circuit debugger). Two examples of research prototype tools are Aveksha<sup id="cite_ref-21" class="reference"><a href="#cite_note-21"><span class="cite-bracket">[</span>21<span class="cite-bracket">]</span></a></sup> and Flocklab.<sup id="cite_ref-22" class="reference"><a href="#cite_note-22"><span class="cite-bracket">[</span>22<span class="cite-bracket">]</span></a></sup> They all leverage a functionality available on low-cost embedded processors, an On-Chip Debug Module (OCDM), whose signals are exposed through a standard <a href="JTAG" title="JTAG">JTAG interface</a>. They are benchmarked based on how much change to the application is needed and the rate of events that they can keep up with.

</p><p>In addition to the typical task of identifying bugs in the system, embedded system debugging also seeks to collect information about the operating states of the system that may then be used to analyze the system: to find ways to boost its performance or to optimize other important characteristics (e.g. energy consumption, reliability, real-time response, etc.).

</p>

<div class="mw-heading mw-heading2"><h2 id="Anti-debugging">Anti-debugging</h2></div>

<p>Anti-debugging is "the implementation of one or more techniques within computer code that hinders attempts at <a href="Reverse_engineering" title="Reverse engineering">reverse engineering</a> or debugging a target process".<sup id="cite_ref-veracode-antidebugging_23-0" class="reference"><a href="#cite_note-veracode-antidebugging-23"><span class="cite-bracket">[</span>23<span class="cite-bracket">]</span></a></sup> It is actively used by recognized publishers in <a href="Copy_protection" title="Copy protection">copy-protection</a> schemas, but is also used by <a href="Malware" title="Malware">malware</a> to complicate its detection and elimination.<sup id="cite_ref-soft-prot_24-0" class="reference"><a href="#cite_note-soft-prot-24"><span class="cite-bracket">[</span>24<span class="cite-bracket">]</span></a></sup> Techniques used in anti-debugging include:

</p>

<ul><li>API-based: check for the existence of a debugger using system information</li>

<li>Exception-based: check to see if exceptions are interfered with</li>

<li>Process and thread blocks: check whether process and thread blocks have been manipulated</li>

<li>Modified code: check for code modifications made by a debugger handling software breakpoints</li>

<li>Hardware- and register-based: check for hardware breakpoints and CPU registers</li>

<li>Timing and latency: check the time taken for the execution of instructions</li>

<li>Detecting and penalizing debugger<sup id="cite_ref-soft-prot_24-1" class="reference"><a href="#cite_note-soft-prot-24"><span class="cite-bracket">[</span>24<span class="cite-bracket">]</span></a></sup></li></ul>

<p>An early example of anti-debugging existed in early versions of <a href="Microsoft_Word" title="Microsoft Word">Microsoft Word</a> which, if a debugger was detected, produced a message that said, "The tree of evil bears bitter fruit. Now trashing program disk.", after which it caused the floppy disk drive to emit alarming noises with the intent of scaring the user away from attempting it again.<sup id="cite_ref-SecurityEngineeringRA_25-0" class="reference"><a href="#cite_note-SecurityEngineeringRA-25"><span class="cite-bracket">[</span>25<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-toastytech_26-0" class="reference"><a href="#cite_note-toastytech-26"><span class="cite-bracket">[</span>26<span class="cite-bracket">]</span></a></sup>

</p>

/* start https://en.wikipedia.org/ */

.mw-parser-output .div-col{margin-top:0.3em;column-width:30em}.mw-parser-output .div-col-small{font-size:90%}.mw-parser-output .div-col-rules{column-rule:1px solid #aaa}.mw-parser-output .div-col dl,.mw-parser-output .div-col ol,.mw-parser-output .div-col ul{margin-top:0}.mw-parser-output .div-col li,.mw-parser-output .div-col dd{page-break-inside:avoid;break-inside:avoid-column}

/* end https://en.wikipedia.org/ */

</style><div class="div-col" style="column-width: 20em;">

<ul><li><a href="Assertion_(software_development)" title="Assertion (software development)">Assertion (software development)</a></li>

<li><a href="Debugging_pattern" title="Debugging pattern">Debugging pattern</a></li>

<li><a href="Magic_number_(programming)#Magic_debug_values" title="Magic number (programming)">Magic debug values</a></li>

<li><a href="Shotgun_debugging" title="Shotgun debugging">Shotgun debugging</a></li>

<li><a href="Software_bug" title="Software bug">Software bug</a></li>

<li><a href="Software_testing" title="Software testing">Software testing</a></li>

<li><a href="Time_travel_debugging" title="Time travel debugging">Time travel debugging</a></li>

<li><a href="Trace_table" title="Trace table">Trace table</a></li>

<li><a href="Troubleshooting" title="Troubleshooting">Troubleshooting</a></li></ul>

</div>

<div class="mw-heading mw-heading2"><h2 id="References">References</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}

/* end https://en.wikipedia.org/ */

</style><div class="reflist reflist-columns references-column-width" style="column-width: 30em;">

/* start https://en.wikipedia.org/ */

.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("./mw/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("./mw/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("./mw/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("./mw/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}

/* end https://en.wikipedia.org/ */

</style><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://books.google.com/books?id=JT0EAAAAMBAJ&pg=RA1-PA33">"InfoWorld Oct 5, 1981"</a>. 5 October 1981. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20190918012636/https://books.google.com/books?id=JT0EAAAAMBAJ&pg=RA1-PA33&lpg=RA1-PA33&focus=viewport">Archived</a> from the original on September 18, 2019<span class="reference-accessdate">. Retrieved <span class="nowrap">July 17,</span> 2019</span>.</cite></span>

</li>

<li id="cite_note-2"><span class="mw-cite-backlink"><b><a href="#cite_ref-2">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://bancroft.berkeley.edu/Exhibits/physics/images/bigscience25.jpg">"Archived copy"</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20191121001830/https://bancroft.berkeley.edu/Exhibits/physics/images/bigscience25.jpg">Archived</a> from the original on 2019-11-21<span class="reference-accessdate">. Retrieved <span class="nowrap">2019-12-17</span></span>.</cite><span class="cs1-maint citation-comment"><code class="cs1-code">{{cite web}}</code>: CS1 maint: archived copy as title (link)</span></span>

</li>

<li id="cite_note-3"><span class="mw-cite-backlink"><b><a href="#cite_ref-3">^</a></b></span> <span class="reference-text">S. Gill, <a rel="nofollow" class="external text" href="https://www.jstor.org/stable/98663">The Diagnosis of Mistakes in Programmes on the EDSAC</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20200306083748/https://www.jstor.org/stable/98663">Archived</a> 2020-03-06 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a>, Proceedings of the Royal Society of London. Series A, Mathematical and Physical Sciences, Vol. 206, No. 1087 (May 22, 1951), pp. 538-554</span>

</li>

<li id="cite_note-4"><span class="mw-cite-backlink"><b><a href="#cite_ref-4">^</a></b></span> <span class="reference-text">Robert V. D. Campbell, <a rel="nofollow" class="external text" href="https://dl.acm.org/citation.cfm?id=609784.609786">Evolution of automatic computation</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20190918012641/https://dl.acm.org/citation.cfm?id=609784.609786">Archived</a> 2019-09-18 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a>, Proceedings of the 1952 ACM national meeting (Pittsburgh), p 29-32, 1952.</span>

</li>

<li id="cite_note-5"><span class="mw-cite-backlink"><b><a href="#cite_ref-5">^</a></b></span> <span class="reference-text">Alex Orden, <a rel="nofollow" class="external text" href="https://dl.acm.org/citation.cfm?id=609784.609793">Solution of systems of linear inequalities on a digital computer</a>, Proceedings of the 1952 ACM national meeting (Pittsburgh), p. 91-95, 1952.</span>

</li>

<li id="cite_note-6"><span class="mw-cite-backlink"><b><a href="#cite_ref-6">^</a></b></span> <span class="reference-text">Howard B. Demuth, John B. Jackson, Edmund Klein, N. Metropolis, Walter Orvedahl, James H. Richardson, <a rel="nofollow" class="external text" href="https://dl.acm.org/citation.cfm?id=808982">MANIAC</a> doi=10.1145/800259.808982, Proceedings of the 1952 ACM national meeting (Toronto), p. 13-16</span>

</li>

<li id="cite_note-7"><span class="mw-cite-backlink"><b><a href="#cite_ref-7">^</a></b></span> <span class="reference-text"><a rel="nofollow" class="external text" href="http://www.bitsavers.org/pdf/mit/ctss/CTSS_ProgrammersGuide.pdf">The Compatible Time-Sharing System</a> <a rel="nofollow" class="external text" href="https://web.archive.org/web/20120527174321/http://www.bitsavers.org/pdf/mit/ctss/CTSS_ProgrammersGuide.pdf">Archived</a> 2012-05-27 at the <a href="Wayback_Machine" title="Wayback Machine">Wayback Machine</a>, M.I.T. Press, 1963</span>

</li>

<li id="cite_note-8"><span class="mw-cite-backlink"><b><a href="#cite_ref-8">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.drdobbs.com/tools/postmortem-debugging/185300443">"Postmortem Debugging"</a>. <i>Dr. Dobb's</i>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20191217045909/https://www.drdobbs.com/tools/postmortem-debugging/185300443">Archived</a> from the original on 2019-12-17<span class="reference-accessdate">. Retrieved <span class="nowrap">2019-12-17</span></span>.</cite></span>

</li>

<li id="cite_note-9"><span class="mw-cite-backlink"><b><a href="#cite_ref-9">^</a></b></span> <span class="reference-text"><cite id="CITEREFE._J._Gauss1982" class="citation journal cs1">E. J. Gauss (1982). <a rel="nofollow" class="external text" href="https://doi.org/10.1145%2F358690.358695">"Pracniques: The 'Wolf Fence' Algorithm for Debugging"</a>. <i>Communications of the ACM</i>. <b>25</b> (11): 780. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<span class="id-lock-free" title="Freely accessible"><a rel="nofollow" class="external text" href="https://doi.org/10.1145%2F358690.358695">10.1145/358690.358695</a></span>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:672811">672811</a>.</cite></span>

</li>

<li id="cite_note-10"><span class="mw-cite-backlink"><b><a href="#cite_ref-10">^</a></b></span> <span class="reference-text"><cite id="CITEREFZeller2005" class="citation book cs1">Zeller, Andreas (2005). <i>Why Programs Fail: A Guide to Systematic Debugging</i>. Morgan Kaufmann. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>1-55860-866-4</bdi>.</cite></span>

</li>

<li id="cite_note-11"><span class="mw-cite-backlink"><b><a href="#cite_ref-11">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20120311131729/http://www.threeriversinstitute.org/HitEmHighHitEmLow.html">"Kent Beck, Hit 'em High, Hit 'em Low: Regression Testing and the Saff Squeeze"</a>. Archived from <a rel="nofollow" class="external text" href="http://www.threeriversinstitute.org/HitEmHighHitEmLow.html">the original</a> on 2012-03-11.</cite></span>

</li>

<li id="cite_note-12"><span class="mw-cite-backlink"><b><a href="#cite_ref-12">^</a></b></span> <span class="reference-text"><cite id="CITEREFRainsberger2022" class="citation web cs1">Rainsberger, J.B. (28 March 2022). <a rel="nofollow" class="external text" href="https://blog.thecodewhisperer.com/permalink/the-saff-squeeze">"The Saff Squeeze"</a>. <i>The Code Whisperer</i><span class="reference-accessdate">. Retrieved <span class="nowrap">28 March</span> 2022</span>.</cite></span>

</li>

<li id="cite_note-13"><span class="mw-cite-backlink"><b><a href="#cite_ref-13">^</a></b></span> <span class="reference-text"><cite id="CITEREFZeller2002" class="citation journal cs1">Zeller, Andreas (2002-11-01). "Isolating cause-effect chains from computer programs". <i>ACM SIGSOFT Software Engineering Notes</i>. <b>27</b> (6): <span class="nowrap">1–</span>10. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1145%2F605466.605468">10.1145/605466.605468</a>. <a href="ISSN_(identifier)" class="mw-redirect" title="ISSN (identifier)">ISSN</a> <a rel="nofollow" class="external text" href="https://search.worldcat.org/issn/0163-5948">0163-5948</a>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:12098165">12098165</a>.</cite></span>

</li>

<li id="cite_note-BondNethercote2007-14"><span class="mw-cite-backlink"><b><a href="#cite_ref-BondNethercote2007_14-0">^</a></b></span> <span class="reference-text"><cite id="CITEREFBondNethercoteKentGuyer2007" class="citation book cs1">Bond, Michael D.; Nethercote, Nicholas; Kent, Stephen W.; Guyer, Samuel Z.; McKinley, Kathryn S. (2007). "Tracking bad apples". <i>Proceedings of the 22nd annual ACM SIGPLAN conference on Object oriented programming systems and applications - OOPSLA '07</i>. p. 405. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1145%2F1297027.1297057">10.1145/1297027.1297057</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>9781595937865</bdi>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:2832749">2832749</a>.</cite></span>

</li>

<li id="cite_note-15"><span class="mw-cite-backlink"><b><a href="#cite_ref-15">^</a></b></span> <span class="reference-text"><cite id="CITEREFRinard2008" class="citation journal cs1">Rinard, Martin C. (2008). "Technical perspective <i>Patching</i> program errors". <i>Communications of the ACM</i>. <b>51</b> (12): 86. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1145%2F1409360.1409381">10.1145/1409360.1409381</a>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:28629846">28629846</a>.</cite></span>

</li>

<li id="cite_note-16"><span class="mw-cite-backlink"><b><a href="#cite_ref-16">^</a></b></span> <span class="reference-text"><cite id="CITEREFHarman2010" class="citation journal cs1">Harman, Mark (2010). "Automated patching techniques". <i>Communications of the ACM</i>. <b>53</b> (5): 108. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1145%2F1735223.1735248">10.1145/1735223.1735248</a>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:9729944">9729944</a>.</cite></span>

</li>

<li id="cite_note-Automatic_bug_fixing_Gazzola2019-17"><span class="mw-cite-backlink">^ <a href="#cite_ref-Automatic_bug_fixing_Gazzola2019_17-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-Automatic_bug_fixing_Gazzola2019_17-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text"><cite id="CITEREFGazzolaMicucciMariani2019" class="citation journal cs1">Gazzola, Luca; Micucci, Daniela; Mariani, Leonardo (2019). <a rel="nofollow" class="external text" href="https://boa.unimib.it/bitstream/10281/184798/2/08089448_final.pdf">"Automatic Software Repair: A Survey"</a> <span class="cs1-format">(PDF)</span>. <i>IEEE Transactions on Software Engineering</i>. <b>45</b> (1): <span class="nowrap">34–</span>67. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<span class="id-lock-free" title="Freely accessible"><a rel="nofollow" class="external text" href="https://doi.org/10.1109%2FTSE.2017.2755013">10.1109/TSE.2017.2755013</a></span>. <a href="Hdl_(identifier)" class="mw-redirect" title="Hdl (identifier)">hdl</a>:<a rel="nofollow" class="external text" href="https://hdl.handle.net/10281%2F184798">10281/184798</a>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:57764123">57764123</a>.</cite></span>

</li>

<li id="cite_note-18"><span class="mw-cite-backlink"><b><a href="#cite_ref-18">^</a></b></span> <span class="reference-text"><cite id="CITEREFTanRoychoudhury2015" class="citation book cs1">Tan, Shin Hwei; Roychoudhury, Abhik (2015). "relifix: Automated repair of software regressions". <i>2015 IEEE/ACM 37th IEEE International Conference on Software Engineering</i>. IEEE. pp. <span class="nowrap">471–</span>482. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1109%2FICSE.2015.65">10.1109/ICSE.2015.65</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-1-4799-1934-5</bdi>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:17125466">17125466</a>.</cite></span>

</li>

<li id="cite_note-19"><span class="mw-cite-backlink"><b><a href="#cite_ref-19">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.ghs.com/products/supertraceprobe.html">"SuperTrace Probe hardware debugger"</a>. <i>www.ghs.com</i>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20171201031136/https://www.ghs.com/products/supertraceprobe.html">Archived</a> from the original on 2017-12-01<span class="reference-accessdate">. Retrieved <span class="nowrap">2017-11-25</span></span>.</cite></span>

</li>

<li id="cite_note-20"><span class="mw-cite-backlink"><b><a href="#cite_ref-20">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://www.lauterbach.com">"Debugger and real-time trace tools"</a>. <i>www.lauterbach.com</i>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20220125072945/https://www.lauterbach.com/frames.html?home.html">Archived</a> from the original on 2022-01-25<span class="reference-accessdate">. Retrieved <span class="nowrap">2020-06-05</span></span>.</cite></span>

</li>

<li id="cite_note-21"><span class="mw-cite-backlink"><b><a href="#cite_ref-21">^</a></b></span> <span class="reference-text"><cite id="CITEREFTancretiHossainBagchiRaghunathan2011" class="citation book cs1">Tancreti, Matthew; Hossain, Mohammad Sajjad; Bagchi, Saurabh; Raghunathan, Vijay (2011). "Aveksha". <i>Proceedings of the 9th ACM Conference on Embedded Networked Sensor Systems</i>. SenSys '11. New York, NY, USA: ACM. pp. <span class="nowrap">288–</span>301. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1145%2F2070942.2070972">10.1145/2070942.2070972</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>9781450307185</bdi>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:14769602">14769602</a>.</cite></span>

</li>

<li id="cite_note-22"><span class="mw-cite-backlink"><b><a href="#cite_ref-22">^</a></b></span> <span class="reference-text"><cite id="CITEREFLimFerrariZimmerlingWalser2013" class="citation book cs1">Lim, Roman; Ferrari, Federico; Zimmerling, Marco; Walser, Christoph; Sommer, Philipp; Beutel, Jan (2013). "FlockLab". <i>Proceedings of the 12th international conference on Information processing in sensor networks</i>. IPSN '13. New York, NY, USA: ACM. pp. <span class="nowrap">153–</span>166. <a href="Doi_(identifier)" class="mw-redirect" title="Doi (identifier)">doi</a>:<a rel="nofollow" class="external text" href="https://doi.org/10.1145%2F2461381.2461402">10.1145/2461381.2461402</a>. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>9781450319591</bdi>. <a href="S2CID_(identifier)" class="mw-redirect" title="S2CID (identifier)">S2CID</a> <a rel="nofollow" class="external text" href="https://api.semanticscholar.org/CorpusID:447045">447045</a>.</cite></span>

</li>

<li id="cite_note-veracode-antidebugging-23"><span class="mw-cite-backlink"><b><a href="#cite_ref-veracode-antidebugging_23-0">^</a></b></span> <span class="reference-text"><cite id="CITEREFShields2008" class="citation web cs1">Shields, Tyler (2008-12-02). <a rel="nofollow" class="external text" href="https://www.veracode.com/blog/2008/12/anti-debugging-series-part-i">"Anti-Debugging Series – Part I"</a>. <i><a href="Veracode" title="Veracode">Veracode</a></i>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20161019075351/http://www.veracode.com/blog/2008/12/anti-debugging-series-part-i">Archived</a> from the original on 2016-10-19<span class="reference-accessdate">. Retrieved <span class="nowrap">2009-03-17</span></span>.</cite></span>

</li>

<li id="cite_note-soft-prot-24"><span class="mw-cite-backlink">^ <a href="#cite_ref-soft-prot_24-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-soft-prot_24-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="https://web.archive.org/web/20111001172453/http://people.seas.harvard.edu/~mgagnon/software_protection_through_anti_debugging.pdf">"Software Protection through Anti-Debugging Michael N Gagnon, Stephen Taylor, Anup Ghosh"</a> <span class="cs1-format">(PDF)</span>. Archived from <a rel="nofollow" class="external text" href="http://people.seas.harvard.edu/~mgagnon/software_protection_through_anti_debugging.pdf">the original</a> <span class="cs1-format">(PDF)</span> on 2011-10-01<span class="reference-accessdate">. Retrieved <span class="nowrap">2010-10-25</span></span>.</cite></span>

</li>

<li id="cite_note-SecurityEngineeringRA-25"><span class="mw-cite-backlink"><b><a href="#cite_ref-SecurityEngineeringRA_25-0">^</a></b></span> <span class="reference-text"><cite id="CITEREFRoss_J._Anderson2001" class="citation book cs1"><a href="Ross_J._Anderson" title="Ross J. Anderson">Ross J. Anderson</a> (2001-03-23). <span class="id-lock-registration" title="Free registration required"><a rel="nofollow" class="external text" href="https://archive.org/details/securityengineer00ande"><i>Security Engineering</i></a></span>. Wiley. p. 684. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>0-471-38922-6</bdi>.</cite></span>

</li>

<li id="cite_note-toastytech-26"><span class="mw-cite-backlink"><b><a href="#cite_ref-toastytech_26-0">^</a></b></span> <span class="reference-text"><cite class="citation web cs1"><a rel="nofollow" class="external text" href="http://toastytech.com/guis/word1153.html">"Microsoft Word for DOS 1.15"</a>. <a rel="nofollow" class="external text" href="https://web.archive.org/web/20130514033750/http://toastytech.com/guis/word1153.html">Archived</a> from the original on 2013-05-14<span class="reference-accessdate">. Retrieved <span class="nowrap">2013-06-22</span></span>.</cite></span>

</li>

</ol></div>

<div class="mw-heading mw-heading2"><h2 id="Further_reading">Further reading</h2></div>

<ul><li><cite id="CITEREFAgans2002" class="citation book cs1">Agans, David J. (2002). <a rel="nofollow" class="external text" href="https://archive.org/details/debugging9indisp0000agan"><i>Debugging: The Nine Indispensable Rules for Finding Even the Most Elusive Software and Hardware Problems</i></a>. AMACOM. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>0-8144-7168-4</bdi>.</cite></li>

<li><cite id="CITEREFBlunden2003" class="citation book cs1"><a href="Bill_Blunden_(author)" title="Bill Blunden (author)">Blunden, Bill</a> (2003). <i>Software Exorcism: A Handbook for Debugging and Optimizing Legacy Code</i>. APress. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>1-59059-234-4</bdi>.</cite></li>

<li><cite id="CITEREFFordTeorey2002" class="citation book cs1">Ford, Ann R.; Teorey, Toby J. (2002). <a rel="nofollow" class="external text" href="https://archive.org/details/practicaldebuggi00ford"><i>Practical Debugging in C++</i></a>. Prentice Hall. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>0-13-065394-2</bdi>.</cite></li>

<li><cite id="CITEREFGrötkerHoltmannKedingWloka2012" class="citation book cs1">Grötker, Thorsten; Holtmann, Ulrich; Keding, Holger; Wloka, Markus (2012). <i>The Developer's Guide to Debugging, Second Edition</i>. Createspace. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-1-4701-8552-7</bdi>.</cite></li>

<li><cite id="CITEREFMetzger2003" class="citation book cs1">Metzger, Robert C. (2003). <i>Debugging by Thinking: A Multidisciplinary Approach</i>. Digital Press. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>1-55558-307-5</bdi>.</cite></li>

<li><cite id="CITEREFMyers2004" class="citation book cs1">Myers, Glenford J (2004). <a rel="nofollow" class="external text" href="https://archive.org/details/artofsoftwaretes00myer"><i>The Art of Software Testing</i></a>. John Wiley & Sons Inc. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>0-471-04328-1</bdi>.</cite></li>

<li><cite id="CITEREFRobbins2000" class="citation book cs1">Robbins, John (2000). <i>Debugging Applications</i>. Microsoft Press. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>0-7356-0886-5</bdi>.</cite></li>

<li><cite id="CITEREFTellesHsieh2001" class="citation book cs1">Telles, Matthew A.; Hsieh, Yuan (2001). <i>The Science of Debugging</i>. The Coriolis Group. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>1-57610-917-8</bdi>.</cite></li>

<li><cite id="CITEREFVostokov2008" class="citation book cs1">Vostokov, Dmitry (2008). <i>Memory Dump Analysis Anthology Volume 1</i>. OpenTask. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-9558328-0-2</bdi>.</cite></li>

<li><cite id="CITEREFZeller2009" class="citation book cs1">Zeller, Andreas (2009). <i>Why Programs Fail, Second Edition: A Guide to Systematic Debugging</i>. Morgan Kaufmann. <a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a> <bdi>978-0-1237-4515-6</bdi>.</cite></li>

<li>Peggy Aldrich Kidwell, <a rel="nofollow" class="external text" href="https://ieeexplore.ieee.org/document/728224?tp=&arnumber=728224&isnumber=15706">Stalking the Elusive Computer Bug</a>, IEEE Annals of the History of Computing, 1998.</li></ul>

<div class="mw-heading mw-heading2"><h2 id="External_links">External links</h2></div>

/* start https://en.wikipedia.org/ */

.mw-parser-output .side-box{margin:4px 0;box-sizing:border-box;border:1px solid #aaa;font-size:88%;line-height:1.25em;background-color:var(--background-color-interactive-subtle,#f8f9fa);display:flow-root}.mw-parser-output .infobox .side-box{font-size:100%}.mw-parser-output .side-box-abovebelow,.mw-parser-output .side-box-text{padding:0.25em 0.9em}.mw-parser-output .side-box-image{padding:2px 0 2px 0.9em;text-align:center}.mw-parser-output .side-box-imageright{padding:2px 0.9em 2px 0;text-align:center}@media(min-width:500px){.mw-parser-output .side-box-flex{display:flex;align-items:center}.mw-parser-output .side-box-text{flex:1;min-width:0}}@media(min-width:720px){.mw-parser-output .side-box{width:238px}.mw-parser-output .side-box-right{clear:right;float:right;margin-left:1em}.mw-parser-output .side-box-left{margin-right:1em}}

/* end https://en.wikipedia.org/ */

</style><style data-mw-deduplicate="TemplateStyles:r1237033735">

/* start https://en.wikipedia.org/ */

@media print{body.ns-0 .mw-parser-output .sistersitebox{display:none!important}}@media screen{html.skin-theme-clientpref-night .mw-parser-output .sistersitebox img[src*="Wiktionary-logo-en-v2.svg"]{background-color:white}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .sistersitebox img[src*="Wiktionary-logo-en-v2.svg"]{background-color:white}}

/* end https://en.wikipedia.org/ */

</style><div class="side-box side-box-right sistersitebox"><style data-mw-deduplicate="TemplateStyles:r1126788409">

/* start https://en.wikipedia.org/ */

.mw-parser-output .plainlist ol,.mw-parser-output .plainlist ul{line-height:inherit;list-style:none;margin:0;padding:0}.mw-parser-output .plainlist ol li,.mw-parser-output .plainlist ul li{margin-bottom:0}

/* end https://en.wikipedia.org/ */

</style>

<div class="side-box-text plainlist">Wikiquote has quotations related to <i><b><a href="https://en.wikiquote.org/wiki/Programming#Debugging" class="extiw external" title="q:Programming">Debugging</a></b></i>.</div></div>

</div>

<div class="side-box-text plainlist">The Wikibook <i><a href="https://en.wikibooks.org/wiki/Computer_Programming_Principles" class="extiw external" title="wikibooks:Computer Programming Principles">Computer Programming Principles</a></i> has a page on the topic of: <i><b><a href="https://en.wikibooks.org/wiki/Computer_Programming_Principles/Maintaining/Debugging" class="extiw external" title="wikibooks:Computer Programming Principles/Maintaining/Debugging">Debugging</a></b></i></div></div>

</div>

<ul><li><a rel="nofollow" class="external text" href="http://www.dumpanalysis.org/">Crash dump analysis patterns</a> – in-depth articles on analyzing and finding bugs in crash dumps</li>

<li><a rel="nofollow" class="external text" href="https://www.cs.usfca.edu/~parrt/doc/debugging.html">The Essentials of Debugging</a> – how to improve your debugging skills</li>

<li><a rel="nofollow" class="external text" href="http://www.clarinox.com/docs/whitepapers/EmbeddedDebugger.pdf">Plug-in Based Debugging For Embedded Systems</a></li>

<li><a rel="nofollow" class="external text" href="https://web.archive.org/web/20120112200659/http://www.byteparadigm.com/embedded-systems-test-and-debug---about-digital-input-generation-135.html">Embedded Systems test and debug – about digital input generation</a> – results of a survey about embedded system test and debug, Byte Paradigm (archived from the original on January 12, 2012)</li></ul>

/* start https://en.wikipedia.org/ */

.mw-parser-output .navbox{box-sizing:border-box;border:1px solid #a2a9b1;width:100%;clear:both;font-size:88%;text-align:center;padding:1px;margin:1em auto 0}.mw-parser-output .navbox .navbox{margin-top:0}.mw-parser-output .navbox+.navbox,.mw-parser-output .navbox+.navbox-styles+.navbox{margin-top:-1px}.mw-parser-output .navbox-inner,.mw-parser-output .navbox-subgroup{width:100%}.mw-parser-output .navbox-group,.mw-parser-output .navbox-title,.mw-parser-output .navbox-abovebelow{padding:0.25em 1em;line-height:1.5em;text-align:center}.mw-parser-output .navbox-group{white-space:nowrap;text-align:right}.mw-parser-output .navbox,.mw-parser-output .navbox-subgroup{background-color:#fdfdfd}.mw-parser-output .navbox-list{line-height:1.5em;border-color:#fdfdfd}.mw-parser-output .navbox-list-with-group{text-align:left;border-left-width:2px;border-left-style:solid}.mw-parser-output tr+tr>.navbox-abovebelow,.mw-parser-output tr+tr>.navbox-group,.mw-parser-output tr+tr>.navbox-image,.mw-parser-output tr+tr>.navbox-list{border-top:2px solid #fdfdfd}.mw-parser-output .navbox-title{background-color:#ccf}.mw-parser-output .navbox-abovebelow,.mw-parser-output .navbox-group,.mw-parser-output .navbox-subgroup .navbox-title{background-color:#ddf}.mw-parser-output .navbox-subgroup .navbox-group,.mw-parser-output .navbox-subgroup .navbox-abovebelow{background-color:#e6e6ff}.mw-parser-output .navbox-even{background-color:#f7f7f7}.mw-parser-output .navbox-odd{background-color:transparent}.mw-parser-output .navbox .hlist td dl,.mw-parser-output .navbox .hlist td ol,.mw-parser-output .navbox .hlist td ul,.mw-parser-output .navbox td.hlist dl,.mw-parser-output .navbox td.hlist ol,.mw-parser-output .navbox td.hlist ul{padding:0.125em 0}.mw-parser-output .navbox .navbar{display:block;font-size:100%}.mw-parser-output .navbox-title .navbar{float:left;text-align:left;margin-right:0.5em}body.skin--responsive .mw-parser-output .navbox-image img{max-width:none!important}@media print{body.ns-0 .mw-parser-output .navbox{display:none!important}}

/* end https://en.wikipedia.org/ */

</style><style data-mw-deduplicate="TemplateStyles:r1038841319">

/* start https://en.wikipedia.org/ */

.mw-parser-output .tooltip-dotted{border-bottom:1px dotted;cursor:help}

/* end https://en.wikipedia.org/ */

</style></div><div role="navigation" class="navbox authority-control" aria-labelledby="Authority_control_databases_frameless&#124;text-top&#124;10px&#124;alt=Edit_this_at_Wikidata&#124;link=https&#58;//www.wikidata.org/wiki/Q845566#identifiers&#124;class=noprint&#124;Edit_this_at_Wikidata928" style="padding:3px"><table class="nowraplinks hlist mw-collapsible autocollapse navbox-inner" style="border-spacing:0;background:transparent;color:inherit"><tbody><tr><th scope="col" class="navbox-title" colspan="2"><div id="Authority_control_databases_frameless&#124;text-top&#124;10px&#124;alt=Edit_this_at_Wikidata&#124;link=https&#58;//www.wikidata.org/wiki/Q845566#identifiers&#124;class=noprint&#124;Edit_this_at_Wikidata928" style="font-size:114%;margin:0 4em">Authority control databases </div></th></tr><tr><th scope="row" class="navbox-group" style="width:1%">National</th><td class="navbox-list-with-group navbox-list navbox-odd" style="width:100%;padding:0"><div style="padding:0 0.25em"><ul><li><span class="uid"><a rel="nofollow" class="external text" href="https://id.loc.gov/authorities/sh85036145">United States</a></span></li><li><span class="uid"><span class="rt-commentedText tooltip tooltip-dotted" title="ladění softwaru"><a rel="nofollow" class="external text" href="https://aleph.nkp.cz/F/?func=find-c&local_base=aut&ccl_term=ica=ph249423&CON_LNG=ENG">Czech Republic</a></span></span></li><li><span class="uid"><a rel="nofollow" class="external text" href="https://www.nli.org.il/en/authorities/987007543228905171">Israel</a></span></li></ul></div></td></tr><tr><th scope="row" class="navbox-group" style="width:1%">Other</th><td class="navbox-list-with-group navbox-list navbox-even" style="width:100%;padding:0"><div style="padding:0 0.25em"><ul><li><span class="uid"><a rel="nofollow" class="external text" href="https://lux.collections.yale.edu/view/concept/366f1890-aaeb-4d4f-9d21-ade170101fcc">Yale LUX</a></span></li></ul></div></td></tr></tbody></table></div></div><div><div class="zim-footer">

This article is issued from <a class="external text" title="Last edited on 2025-05-04" href="https://en.wikipedia.org/wiki/?title=Debugging&oldid=1288723587">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.

</div>

</div></div>

</div>

</main>

</div>

</body></html>